docs: correct terminology from 'tasks' to 'modes' in sticky models se…#144
Merged
Conversation
…ction for consistency
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
There was a problem hiding this comment.
👍 Looks good to me! Reviewed everything up to 6b7fb14 in 51 seconds
More details
- Looked at
13lines of code in1files - Skipped
0files when reviewing. - Skipped posting
3drafted comments based on config settings.
1. docs/basic-usage/using-modes.md:6
- Draft comment:
Good update: changing 'tasks' to 'modes' clearly aligns the terminology across documentation. Ensure all related docs use the same consistent terminology. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =20%<= threshold50%
This comment is asking the author to ensure consistency in terminology across documentation. It doesn't provide a specific code suggestion or point out a specific issue in the code itself. It seems to be more of a general request for consistency, which doesn't align with the rules provided.
2. docs/basic-usage/using-modes.md:6
- Draft comment:
Renamed 'tasks' to 'modes' for consistency with the rest of the documentation. Please ensure that all similar references are updated accordingly. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%
The comment is asking the PR author to ensure that all similar references are updated, which violates the rule against asking the author to double-check things. The comment is not making a specific code suggestion or pointing out a specific issue, but rather giving a general instruction.
3. docs/basic-usage/using-modes.md:5
- Draft comment:
There's a typographical error in the admonition block declaration on line 5. The markdown syntax for an info block typically requires three colons (:::info Sticky Models) instead of four (::::info Sticky Models). Please correct it. - Reason this comment was not posted:
Comment was on unchanged code.
Workflow ID: wflow_SPvNiPnv7goHG70F
You can teach Ellipsis what to look for with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ction for consistency
Important
Corrects terminology from 'tasks' to 'modes' in
using-modes.mdfor consistency.using-modes.mdfor consistency in the Sticky Models section.This description was created by
for 6b7fb14. You can customize this summary. It will automatically update as commits are pushed.